Repository navigation
POC: the answer-again cap is the loop's again flag - #3825
Closed
cursor[bot] wants to merge 5 commits into
Closed
cursor[bot] wants to merge 5 commits into
cursor[bot] wants to merge 5 commits into
Conversation
… while it answered
- orchestration: takeOwedNotice takes an owed notice in the running
request's name through onTaskSettled's take record (shared takeFor).
- workforce: takeFinishedTasks (person's turn only), handled by the same
steps as the queued onTaskSettled (settleTakenNotice), and
finishedTasksAnswerAgain, the pre-built source.
- planned's answer-once-more becomes one answer-again step with two
sources (the plan, the flow's) under MAX_ANSWERS_AGAIN, on doWhile.
- defineAgentWorkerFlow({ answerAgain: true | block }).
- Goal: goals/hand-offs/result-reaches-the-running-turn.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N9RvCHba2QKPohNxnZNzct
…ce (FIX-2159) Workforce README: the answerAgain option, the finished-tasks source, its limits and exports. Orchestration README: taking an owed notice in a running request. Goal verdict log: PASS at af14e78b. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N9RvCHba2QKPohNxnZNzct
…test (FIX-2159) "user" for the signed-in user, and a test helper not named like the retired ask mark, so the Process guards pass. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N9RvCHba2QKPohNxnZNzct
…out takeNotice (FIX-2159) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N9RvCHba2QKPohNxnZNzct
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
The open-round flag only existed so a round past MAX_ANSWERS_AGAIN could start and skip its sources. The loop already stops when again is false, so that flag is the cap. This branch does not merge. Co-authored-by: Jake Hoffner <jhoffner@users.noreply.github.com>
cursor
Bot
force-pushed
the
poc/shorter-answer-again
branch
from
October 24, 2026 00:22
4b746f1 to
fdf7863
Compare
jhoffner
pushed a commit
that referenced
this pull request
Oct 24, 2026
The round-open flag only let a round past MAX_ANSWERS_AGAIN start and then skip its sources. The loop already stops when a round says not to look again, so the last counted answer says so and no further source runs. A round's consumed messages are cleared with the answer that used them, and decidePlan clears them for a fresh turn. Folds the subtraction proposed in #3825. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N9RvCHba2QKPohNxnZNzct
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Code Snob. This PR does not merge.
The answer-again loop on #3823 keeps a second request flag,
answerRoundOpen, so a round pastMAX_ANSWERS_AGAINcan start and then skip its sources. The loop already stops whenagainis false. That flag is the cap.What this subtracts
answerRoundOpen, theroundOpenpredicate, andanswer-again-open-round. After the last counted answer,againis false, so no further source runs. A round clears the messages it consumed when it counts the answer, which is what stops the plan's message being asked again.Fold
4b746f18contoba5415c6(claude/project-thread-uzb61a). Do not reset onto this branch. Close this PR unmerged after #3823 lands.What still passes
Same contract: the cap stays 3, the plan's answer still counts, both sources still join into one answer, and a source still does not run after the cap. No take, notice, or turn-gating change.
answer-again-finished-tasks9 passedworker-plans-its-steps22 passedplan.tspassedRed:
answered <= MAX_ANSWERS_AGAINanswered 4 times (expected 3).Net −12 (
plan.ts, +16/−28).